dist: bump rustup version to v1.29.0
#4513
Conversation
|
PS: I understand that this version is not final, but any suggestion regarding the wording/phrasing/format of the changelog is greatly appreciated :) |
CHANGELOG.md
Outdated
| - `rustup update` and `rustup toolchain` subcommands will download toolchain | ||
| components concurrently. [pr#4436] | ||
|
|
||
| - You can use the `RUSTUP_CONCURRENT_DOWNLOADS` |
There was a problem hiding this comment.
Is this discoverable in some other way? If not, how do we make it discoverable?
There was a problem hiding this comment.
@djc I think we must achieve a careful balance between not spamming the users and improving discoverability. I'm not sure about other potential solutions, but printing a hint every time the download is activated seems like a no-go to me (meaning myself as a user would not want that, and other tools like APT and Docker Compose seemingly are giving no similar hints).
Idem for other options regarding the download.
There was a problem hiding this comment.
@djc Some applications show random tips for such cases (I'm thinking of certain video games), maybe we can apply the same techniques somehow and allow it to be hidden at the same time?
The rationale is that these tips are not essential to 99% of the OOTB experience of our app; if users are interested in tuning for their specific environment then after a certain period of time they will know enough information about it.
There was a problem hiding this comment.
Pff, not sure I'd be a fan of random tips. I'm thinking more of relevant error messages, the help stuff for relevant CLI commands and maybe other places in the documentation.
rami3l
force-pushed
the
dist/release-1-29.0
branch
3 times, most recently
from
48eaccf to
bcc97ee
Compare
rami3l
force-pushed
the
dist/release-1-29.0
branch
from
bcc97ee to
ac5c68f
Compare
This is the 1st PR for the
1.29.0beta release according to our release process.Checklist
Draft the release blog post.(Not required, since this is a beta release.)